Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1471

reference
384-tree-1
name
1471
tree-preservation-order

undefined

384-tpo-1
uprn
address-text
point
POINT (-1.026515 50.884187)
geometry
MULTIPOLYGON (((-1.026430 50.884178,-1.026434 50.884195,-1.026446 50.884210,-1.026465 50.884222,-1.026488 50.884230,-1.026514 50.884233,-1.026541 50.884230,-1.026565 50.884223,-1.026584 50.884211,-1.026596 50.884196,-1.026601 50.884179,-1.026597 50.884163,-1.026585 50.884147,-1.026567 50.884135,-1.026543 50.884128,-1.026517 50.884125,-1.026490 50.884127,-1.026466 50.884135,-1.026447 50.884146,-1.026435 50.884161,-1.026430 50.884178)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL